[tests-only] Be more specific matching an expected-failure #4618
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
phil-davis
added
Status:Needs-release
and removed
Status:Needs-Review
delete-merged-branch
bot
deleted the
adjust-match-for-expected-failures
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Be more specific in matching the format
[someSuite/someFeature.feature:42]of an expected-failure.Do not assume that it is preceded by a
-and a single space. Codacy inowncloud/ociscomplains a lot about.mdfile format and insists on particular spacing. So we do not want to depend on the exact spacing of this sort of thing.Related Issue
How Has This Been Tested?
CI
Types of changes
Checklist: